Repository navigation
docs(upstream): validate roadmap receipts and add Browser Harness pilot - #32
Merged
Merged
Conversation
xLagerFeuer
force-pushed
the
docs/roadmap-standardization-route-20261117
branch
from
November 17, 2026 16:15
75f56ba to
3a90d00
Compare
Source-pinned noncanonical example with structural checks; no grade or cost claim. Tested: 116 unit, protocol and roadmap validators.
xLagerFeuer
force-pushed
the
docs/roadmap-receipt-pilot-20261117
branch
from
November 17, 2026 16:15
09139d6 to
1704d2e
Compare
Base automatically changed from
docs/roadmap-standardization-route-20261117
to
main
November 17, 2026 16:16
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to merged PR #31
Completes the architecture-first Upstream roadmap work by adding a source-pinned, non-canonical Browser Harness roadmap pilot, a fail-closed Markdown receipt validator and guidance preserving existing fork/Upgrade authority.
Changes
docs/examples/browser-harness-roadmap-20261117.md: dated example distinguishing historical accepted IndexA C — — — —, unmerged Index reassessment #3219, original HEAD, source issues/PRs and unverified functional opportunities. S3=C is only a proposed target, not an existing capability.scripts/validate_capability_roadmap.pyand seven tests: check required sections, pinned source/review SHAs, report disposition,NOT_MEASUREDandDRAFT — NOT PUBLISHED. Structural only: not live source, legal, VSM or cost verification.docs/CAPABILITY_ROADMAP.md,docs/FORK_METADATA.mdanddocs/UPGRADE_PR_REVIEW.md: roadmap records are not new state/assessment ledgers; implementation still requires original-native tests, v2 contribution provenance, exact five-link fork review and publication approvals.Validation
Local rebased content matches GitHub-uploaded blob/tree SHAs. 116/116 tests PASS,
scripts/validate_contract.pyPASS, pilot structural validator PASS,git diff --checkPASS. Originalbrowser-userepository and forks untouched.Part 1: #31 (merged). This PR is now based on
mainand contains only the second package. No release/version bump or evidence-based savings claim.